Simplified mobile communication device

ABSTRACT

A first communication device is detected as being substantially collocated with a second communication device using a short-range wireless network. A connection is established between the first and second communication devices over the short-range wireless network. In some instances, authentication data can be sent from the second communication device to the first communication device to authenticate a user to the first communication device. Further, input is received from the first communication device over the short-range wireless network specifying a telephone number for a telephone call using the second communication device. A connection is established between the second communication device and a cellular base station to initiate the telephone call with a third communication device associated with the telephone number. In some instances, the second communication device is a wireless headset device.

TECHNICAL FIELD

This disclosure relates in general to the field of communications and,more particularly, to mobile communication devices.

BACKGROUND

With the sale, production, and deployment of mobile phones and otherhandheld and mobile computing devices eclipsing more traditional desktoppersonal computing devices, consumers and users have come to expectincreased mobility in their access to computer applications, theInternet, digital communications, and other software services andresources. This increased demand has contributed to a correspondingacceleration in developments and advancements within mobile computingdevices. Service providers and device manufacturers, carriers, andretailers have developed business models in some cases encouraging thepurchase of new devices, with some customers electing to purchase orreplace new devices, such as new cell phones and smart phones, multipletimes per year to keep pace with the latest models and featureofferings. Aside from the financial commitment of purchasing multipledevices, migrating and reproducing data and programs from one mobiledevice to another newer device can be difficult and inconvenient.

Mobile computing devices can connect to multiple different networksusing a variety of protocols. Mobile computing devices exist that areadapted to connect to WiFi networks, wireless broadband networks (suchas 3G, 4G, LTE, and other cellular networks), as well as short rangenetworks such as Bluetooth piconets. Peripheral devices have beendeveloped for mobile computing devices such as smartphones and othermobile phones, such as Bluetooth hands-free headset devices, allowing auser to send and receive voice data to their mobile phone using theheadset device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified schematic diagram of an example computing systemincluding one or more simplified cellular telephone devices operating inconnection with one or more cooperating computing devices in accordancewith one embodiment;

FIG. 2 is a simplified block diagram of an example simplified cellulartelephone device and an example cooperating computing device inaccordance with one embodiment;

FIGS. 3A-3B are simplified block diagrams illustrating exampleoperations including a simplified cellular telephone device inaccordance with some embodiments;

FIGS. 4A-4C are simplified block diagrams illustrating exampleauthentication techniques involving a simplified cellular telephonedevice in accordance with some embodiments;

FIG. 5 is a simplified block diagram of example simplified cellulartelephone devices and example cooperating computing devices inaccordance with one embodiment;

FIGS. 6A-6B are simplified flowcharts illustrating example techniquesfor cooperative interactions between an example simplified cellulartelephone device and another computing device.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

In general, one aspect of the subject matter described in thisspecification can be embodied in methods that include the actions ofdetecting a first communication device as substantially collocated witha wireless headset device using a short-range wireless network andestablishing a connection between the first communication device and thewireless headset device over the short-range wireless network. Input canbe received from the first communication device over the short-rangewireless network specifying a telephone number for a telephone callusing the wireless headset device. A connection can be establishedbetween the wireless headset device and a cellular base station toinitiate the telephone call with a second communication deviceassociated with the telephone number.

Further, in another general aspect, a system can be provided includingat least one processor device, at least one memory element, a shortrange wireless network adapter, and a device coordinator. The devicecoordinator, when executed by the processor, can detect a firstcommunication device as substantially collocated with the apparatususing a short-range wireless network, establish a connection with thefirst communication device over the short-range wireless network, andcommunicate the user authentication data to the first communicationdevice over the short-range wireless network to authenticate aparticular user to the first communication device. In some instances,the system can further include a microphone, speaker, and cellularadapter including an antenna and adapted to establish a connection witha cellular base station to initiate the telephone call with a secondcommunication device associated with the telephone number.

Further, in another general aspect, subject matter described in thisspecification can be embodied in methods that include the actions ofdetecting a first communication device as substantially collocated witha second communication device using a short-range wireless network,establishing a connection between the first communication device and thesecond communication device over the short-range wireless network, andreceiving authentication data from the first communication device overthe short-range wireless network. The authentication data can be used toauthenticate a particular user to the second communication device.Thereafter, a telephone number can be sent to the first communicationdevice for use by the first communication device in establishing atelephone call with another device associated with the telephone number.

These and other embodiments can each optionally include one or more ofthe following features. The apparatus can include a wireless headsetdevice. The wireless headset device can be adapted to capture voiceinputs and output audio. The apparatus can further include a voicerecognition module adapted to authenticate a user based on voice inputsreceived at the microphone. The apparatus can lack tactile inputinterfaces and a graphical user display. Voice inputs can be received atthe wireless headset device and voice data can be sent corresponding tothe received voice inputs to the cellular base station in connectionwith the telephone call. The voice data can be sent by the wirelessheadset device. Communications can be received from the secondcommunication device forwarded by a cellular base station in connectionwith the telephone call and audio outputs can be presented at thewireless headset device corresponding to the received communications.Authentication data can be sent from the wireless headset device to thefirst communication device, the authentication data used by the firstcommunication device to authenticate a user to the first communicationdevice. The authentication data can include an encryption key andcontent accessible through the first communication device is decryptedbased at least in part on the received encryption key. Theauthentication data can be sent over the short-range wireless network.The authentication data can include at least one of a digitalcertificate, digital signature, and an encryption key. Authentication ofthe user to the first communication device can include receiving secondauthentication data from the user at the first communication device. Thesecond authentication data can include a personal identification number(PIN) entered by the user at an interface of the first communicationdevice. In some instances, a third communication can be detected assubstantially collocated with the wireless headset device using ashort-range wireless network and a connection can be established betweenthe third communication device and the wireless headset device over ashort-range wireless network. Second input data can be received from thethird communication device over a short-range wireless networkspecifying a telephone number for a second telephone call using thewireless headset device and a connection between the wireless headsetdevice and a cellular base station can be established to initiate thesecond telephone call.

Further, embodiments can each optionally include one or more of thefollowing features. The short-range wireless network can include atleast one of a Bluetooth piconet and a WiFi local area network. Voiceinput can be received from a user and compared against a voice profilefor the user to authenticate the user on the wireless headset devicebased on the comparison. Indeed, a user-entered authentication input canbe received in addition to the authentication data, and both thereceived authentication data and user-entered authentication input canbe used in the authentication of the particular user to a cooperatingcommunication device. The user-entered authentication data input can bea voice sample for comparison with a voice recognition sample for theparticular user or can be a user-entered passkey. User profile data canbe identified corresponding to the particular user based on the receivedauthentication data and access can be provided to the user profile datathrough a user interface of the second communication device. The userprofile data can be identified from a set of profile data associatedwith a plurality of user profiles including a user profile of theparticular user. The user profile data can be hosted by a storage deviceremote from the second communication device and providing access to theuser profile data can include authenticating access to the storagedevice. Use of a cooperating computing device can be locked pendingauthentication to the device using the wireless headset device or othersimplified mobile communication device.

Some or all of the features may be computer-implemented methods orfurther included in respective systems or other devices for performingthis described functionality. The details of these and other features,aspects, and implementations of the present disclosure are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the disclosure will be apparent from thedescription and drawings, and from the claims.

Example Embodiments

FIG. 1 is a simplified block diagram illustrating an exampleimplementation of a computing system 100 including a plurality ofsimplified mobile communication devices (e.g., 105, 110) each capable ofestablishing and participating in communications over one or morecellular communication networks (e.g., 140). Simplified mobilecommunication devices 105, 110 can also establish and participate infurther communications with cooperating computing devices (e.g., 115,120, 125, 130). For instance, simplified mobile communication devices(e.g., 105, 110) can include simplified telephone devices (e.g., 105,110) and can connect to or communicate with other more-robust computingdevices, such as personal digital assistants, tablet computers, laptopor desktop personal computers, smartphones, etc. (e.g., 115, 120, 125,130), over short range communication networks (e.g., 135 a, 135 b) usingsuch technology as WiFi or Bluetooth.

Simplified mobile communication devices 105, 110 can includefunctionality allowing a user to connect to one or more cellular networkbase stations (e.g., 145) to access one or more telephone networks, suchas a public switched telephone network (PSTN) or other telephonenetworks including voice-over-IP (VOIP) networks, push-to-talk networks,etc. The simplified communication device 105, 110 can be used, forinstance, to place, accept, and otherwise participate in telephone callswith other telephone devices (e.g., 155 a-c) over telephone network 145.Simplified mobile communication device 105, 110 can also access datanetworks, such as the Internet 160, over cellular network 140, andaccess and consume applications, services, data, and other resourcesserved by web servers 165 and other devices coupled to the data network160.

In some instances, simplified mobile communication devices 105, 110 mayinclude functionality for engaging in cellular telephone communicationsand presenting and receiving voice data to the user, while providinglittle to no tactile input/output (I/O) functionality on the device 105,110, such as a keypad, touchscreen, or other tactile controls typicallyincluded on cellular telephone devices. Omitting I/O controls, devices,and interfaces capable of receiving tactile input or graphical displayscan allow for the implementation of more compact cellular telephonedevices 105, 110. In some instances, simplified mobile communicationdevices 105, 110 can be adapted to be conveniently carried or worn by auser, thereby more directly connecting the user to the simplified mobilecommunication devices 105, 110 and physically associating the user withthe mobile communication device 105, 110. Indeed, in someimplementations, simplified mobile communication devices 105, 110 can beused as a physical security token for use in authenticating thesimplified mobile communication device's user with particularcooperating computing devices 115, 120, 125, 130 or data, applications,or other digital resources accessible, for instance, using cooperatingcomputing devices 115, 120, 125, 130.

In some instances, a simplified mobile communication device (e.g., 105)can accept inputs from a cooperating computing device (e.g., 115)connected to the simplified mobile communication device over a shortrange wireless network (e.g., 135 a) in connection with the simplifiedmobile communication device's initiation or participation in a telephonecall. For example, simplified mobile communication device 105, in someinstances, may not include a user interface that allows a user to key-ina telephone number, view or select a listing of contacts, or otherwiseselect or view telephone numbers associated with the call. For example,a user can enter a particular telephone number to be called using thesimplified mobile communication device (e.g., 105) using a graphicaluser interface, such as presented on a touchpad display of thecooperating device (e.g., 115). In other instances, cooperatingcomputing devices (e.g., 115) connected to simplified mobilecommunication device (e.g., 105) can be used to display data received bythe simplified mobile communication device (e.g., 105) (for instance,over a data network 160), for example, because simplified mobilecommunication device 105 includes insufficient data rendering andgraphical display capabilities, among other examples.

While simplified mobile communication devices 105, 110, in someimplementations, can be used to access data adapted for display usingone or more rendering applications (such as web browsers) and graphicaldisplay devices not included in the simplified mobile communicationdevice. The simplified mobile communication device can communicate suchdata to cooperating computing devices 115, 120, 125, 130 for renderingand display using the cooperating computing devices 115, 120, 125, 130.In some instances, one or more of the cooperating computing devices 115,120, 125, 130 can also include functionality for connecting to andaccessing web-based resources (e.g., over network 160) independent ofany simplified communication devices (e.g., 105, 110) connected to thecooperating device.

In general, “servers,” “clients,” and “computing devices,” includingcomputing devices used to implement system 100 (e.g., 105, 110, 115,120, 125, 130, 140, 145, 165), can include electronic computing devicesoperable to receive, transmit, process, store, communicate, or managedata and information associated with the software system 100. As used inthis document, the term “computer,” “computing device,” “processor,” or“processing device” is intended to encompass any suitable processingdevice. For example, elements of the system 100 may be implemented usingdistributed computing environments, including parallel processingenvironments, server pools, and cloud computing environments. Further,any, all, or some of the computing devices may be adapted to execute anyoperating system, including Linux, UNIX, Windows Server, etc., mobileoperating system, including Apple iOS™, Google Android™, Windriver™,etc. as well as virtual machines adapted to virtualize execution of aparticular operating system, including mobile, customized, andproprietary operating systems.

Further, servers, clients, and computing devices (e.g., 105, 110, 115,120, 125, 130, 140, 145, 165) can each include one or more processors,computer-readable memory, and one or more interfaces, among otherfeatures and hardware. Servers and computing devices can include anysuitable software component or module, or computing device(s) capable ofhosting and/or serving a software application or services (e.g.,services of web server 165, applications of computing devices 115, 120,125, 130), including mobile, distributed, enterprise, or cloud-basedsoftware applications, data, and services.

Cooperating computing devices 115, 120, 125, 130 can include laptopcomputers, desktop computers, tablet computers, shared computing kiosks,smartphones, personal digital assistants, handheld video game consoles,and other devices capable of connecting wirelessly to a simplifiedmobile communication device (e.g., 105, 110) over a short range network(e.g., 135 a-b). Attributes and functionality of cooperating computingdevices 115, 120, 125, 130 can differ widely from device to device,including the operating systems and collection of software programsloaded, installed, executed, operated, or otherwise accessible to thedevice, as well as the tools, subsystems, controls, display units,speakers, microphones, keypads, mice, trackballs, cameras, network cardsand adapters, graphic cards and adapters, sound cards and adapters, andother components integrated or connected to the cooperating computingdevice. A device can additional include a respective set of programsthat can include operating systems, applications (including “mobileapps”), plug-ins, applets, virtual machines, machine images, drivers,executable files, and other software-based programs capable of beingrun, executed, or otherwise used by the respective cooperating devices(e.g., 115, 120, 125, 130). Some programs and data stored on orotherwise accessible through a cooperating computing device can beassociated with a particular user profile, restricting access toparticular programs to users logged-in or otherwise authenticated inconnection with the user profile.

Each cooperating computing device can include at least one graphicaldisplay device and user interfaces allowing a user to view and interactwith graphical user interfaces (GUIs) of applications and other programsprovided in system 100. In general, cooperating computing devices caninclude any electronic computing device operable to receive, transmit,process, and store any appropriate data associated with the softwareenvironment of FIG. 1. It will be understood that there may be anynumber of endpoint devices associated with system 100, as well as anynumber of endpoint devices external to system 100. Further, the term“client,” “endpoint device,” “mobile device,” and “user” may be usedinterchangeably as appropriate without departing from the scope of thisdisclosure. Moreover, while each cooperating computing device may bedescribed in terms of being used by one user, this disclosurecontemplates that many users may use one computer or that one user mayuse multiple computers.

While FIG. 1 is described as containing or being associated with aplurality of elements, not all elements illustrated within system 100 ofFIG. 1 may be utilized in each alternative implementation of the presentdisclosure. Additionally, one or more of the elements described hereinmay be located external to system 100, while in other instances, certainelements may be included within or as a portion of one or more of theother described elements, as well as other elements not described in theillustrated implementation. Further, certain elements illustrated inFIG. 1 may be combined with other components, as well as used foralternative or additional purposes in addition to those purposesdescribed herein.

Traditional cell phones, smart phones, and other mobile computingdevices allow a user to interact with one or more GUIs of programsinstalled or accessed using the computing device. Some devices comeequipped with cellular network adapters (including receivers,transmitters, antennae, signal processors, and other functionalityallowing users to make telephone calls and connect to data networks(such as the Internet) over cellular networks using the device. Modernsmart phones are examples of such devices. Additionally, peripheraldevices have been developed, such as Bluetooth-enable headsets, whichallow users to take make “hands-free” calls using their cellular devicesover their hands-free peripheral devices.

Such multi-function devices have become feverishly popular in partbecause of the convenient access they provide to a multitude ofcomputing tasks. Users can read, write, send and receive email; generatedocuments; access the Internet; receive GPS directions; make telephonecalls; play video games; send SMS messages; video chat; take videos andphotos; among a continuing stream of evolving functions and uses.Additionally, users are increasingly acquiring and using multiplecomputing devices. For instance, a user may have a smart phone for work,a different personal smart phone, a tablet computer for personal use, alaptop for work, a personal desktop; a video game system; and a mediaserver. Further, as each of these respective devices evolves, users mayreplace and supplement their devices with newer devices with updated oradditional functionality.

Managing data across a multitude of devices can be challenging toconsumers. Users can synchronize devices to some degree in an attempt tokeep some files and data consistent across two or more of their devices,although users often start from scratch when purchasing new devices toreplace an outdated, lost, or broken device, re-loading their data andfavorite software programs onto the new device. Further, traditionalmobile phones and devices are carried in purses, bags, or pockets andare frequently misplaced, lost, or stolen, allowing savvy thieves togain unauthorized access to the owner's data, data and telephoneservice, among other sensitive and valuable assets. Systemimplementations such as that outlined in FIG. 1 can resolve many of theissues identified above, among others.

For instance, turning to FIG. 2, a simplified block diagram 200 is shownof an example system including an example simplified mobilecommunication device 205 and an example cooperative computing device210. The simplified mobile communication device 205 can be a deviceequipped to be easily carried or worn by a user, such as a mobileheadset, that can receive I/O support from cooperating computing device210, for instance, by connecting to and communicating with thecooperating computing device 210 over, for example, a short rangenetwork 135. A wearable device that can be used as a telephone whileworn can mitigate against instances where a mobile phone or device ismade available to potential thieves or unauthorized users, such as ininstances where a device removed from a carrier, or pocket, set on adesk or table, or other unsecure location. Providing for a compact andwearable simplified mobile device can assist in keeping the simplifiedmobile communication device 205 secure and in the proper hands.

A simplified mobile communication device 205 can include one or moreprocessors 215 and memory elements 218 used to execute software stored,downloaded, embodied, or otherwise accessible to the device 205,including signal processing functionality and other operations inassociation with network adapters (e.g., 225, 228) and other modules(e.g., 230, 232) included on mobile communication device 205. In thisparticular example, simplified mobile communication device 205 caninclude additional hardware and software adapted to allow a user toinput and receive audio and voice through the communication device 205.For instance, simplified mobile communication device 205 can include oneor more microphones 220 and speakers 22 for receiving and deliveringvoice and other audio, for instance, during a telephone call made usingthe simplified mobile communication device 205. Indeed, mobilecommunication device 205 can include a cellular adapter 225 adapted toestablish and/or connect to and participate in mobile telephony overcellular communication networks. Cellular adapter 225 can includecircuitry, software, and logic including components foranalog-to-digital and digital-to-analog conversion, digital signalprocessing, radio frequency (RF) amplifiers and controllers, callprocessing logic, among other functionality and components used toenable cellular communications, including data communications overwireless mobile broadband networks. Further, simplified mobilecommunication device 205 can include subscriber identity module (SIM)data (e.g., 242) and other data for use, for instance, by cellularnetworks in identifying the device 205 and a user or servicesubscription associated with the device 205.

In addition to cellular adapter 225, simplified mobile communicationdevice 205 can include additional components and functionality to enablethe communication device 205 to connect and receive data from one ormore cooperating computing devices (e.g., 210) over one or more shortrange networks (e.g., 135). For example, simplified mobile communicationdevice 205 can include a short range network adapter 228, authenticationbroker 230, and device coordinator 232. Short range network adapter 228can be adapted to establish, discover, connect to, and communicate incommunication sessions within one or more different short range wirelessnetworks (e.g., 135), including ad hoc wireless networks establishedusing Bluetooth or WiFi and thereby facilitate the simplified mobilecommunication device's 205 connection to and participation incommunication sessions with cooperating devices over a short rangenetwork, such as a Bluetooth piconet or a WiFi network. A short rangenetwork adapter 228 can further include antennae and other hardware fordiscovering, transmitting, and receiving radio signals to and from otherdevices in connection with participation within a wireless communicationsession over one or more short range wireless networks (e.g., 135).

Simplified mobile communication device 205 may be considered simplifiedin that it lacks most of the functionality available in modern computingdevices, such as personal computers, tablet computers, smart phones, andthe like, while still functioning as a standalone cellular telephonedevice. In some instances, simplified mobile communication device 205include minimal software, in some cases limited to logic for use inengaging in communication sessions over cellular networks (e.g., 140)and short range networks (e.g., 135) with other computing devices (e.g.,165, 210). Further, simplified mobile communication devices 205 may lackrobust user interfaces and lack the ability to accept tactile user inputin connection with the dialing of a phone number or receiving anidentifier of another endpoint in a network. In some instances,simplified communication devices 205, while lacking higher-level tactileinputs, such as a keypad, touchscreen, or the like, may include basictactile inputs for performing basic operations on the simplifiedcommunication device 205 such as a power button or volume control, whilestill lacking higher-level I/O controls. Further, simplified mobilecommunication device 205 may lack a graphical display device adapted forrendering data received, for instance, from data servers 165 or inconnection with one or more programs or data stores of cooperatingcomputing devices (e.g., 210). Due to a lack of tactile UI support andlimited I/O and graphical display capabilities on simplified mobilecommunication devices (e.g., 205), cooperating computing device 210 canlink to and serve as a wireless peripheral I/O device of a companionsimplified mobile communication device 205, allowing dialed phonenumbers, identification of URLs or other address data to be input at thecooperating computing device and forwarded to the simplifiedcommunication device 205 for use by the simplified communication device205 in making telephone calls, contacting remote web and data servers(e.g., 165), and other network endpoints, among other examples.

In some implementations, in addition to serving as a cellular telephonedevice, simplified mobile communication device 205 can also serve as aphysical token for authenticating a user on one or more other computingdevices, such as cooperating computing device 210. Authentication data(e.g., 240) can be sent by the simplified mobile communication device205 to a cooperating computing device 210, for instance, over a shortrange network connection (e.g., 135). Such authentication data can beused to authenticate or otherwise make the cooperating computing device210, or particular data, programs, or user profiles available to theuser of the simplified mobile communication device 205. For instance,authentication data can include a digital signature or certificate,encryption key, or other authentication data. Further, authenticationdata can be dependent on identifying that the simplified mobilecommunication device's 205 is collocated (or within a predeterminedproximity) of the cooperating computing device 210. For instance, a keypresent on the simplified mobile communication device 205 (orcooperating computing device 210) can decrypt data included on thecooperating computing device 210 (or unlock access to the simplifiedmobile communication device 205) based on a determination that thedevice holding the key is in proximity with the device to be decryptedor unlocked using the key. In another example, authentication data canbe implemented or encoded in the hardware of either (or both) of asimplified mobile communication device 205 or cooperating computingdevice 210. In essence, the holder or possessor of the simplified mobilecommunication device 205 can use the mobile communication device 205 toauthenticate the user to a user profile or to a device generally basedon the user's possession of the device 205 (and the exchanging andverification of authentication data stored on the device 205 with acooperating computing device (e.g., 210)).

In one example implementation, simplified mobile communication device205 can include an authentication broker 230 adapted to coordinate thepassing of authentication data 240, as well as other data, such as auser identifier, such as a globally-unique user identifier (GUUID)(e.g., 238), to a cooperating computing device (e.g., 210) in connectionwith a user authenticating to the cooperating computing device 210 byvirtue of the user possessing the mobile communication device 205.Cooperating computing device 210 can include modules, such as anauthentication manager 258 for use in connection with receivingauthentication data (e.g., 240) from a simplified mobile communicationdevice (e.g., 205). For instance, authentication data can be used by thecooperating computing device 210 to authenticate a user to a particularuser profile (such as a profile corresponding to the GUUID 238), decryptdata stored on the cooperating computing device 210, among other usesand examples.

Simplified mobile communication device 205 can further includeadditional modules and functionality. In some instances, a singlesimplified mobile communication device 205 can connect to and operatecooperatively with a plurality of different cooperating devices. Adevice coordinator 232 can be used to manage the simplified mobilecommunication device's 205 cooperation with multiple differentcooperating devices, as well as different types of cooperating devices.In some examples, relationships can be established between a particularsimplified mobile communication device 205 and two or more cooperatingcomputing devices. Device coordinator 232 can be used to identify that apre-existing relationship exists between the simplified mobilecommunication device 205 and a particular cooperating computing device(e.g., based on a previous connection, setup, and/or cooperativeinteraction session between the devices, for instance, over a shortrange network 135 or wireline connection). Other functionality can alsobe provided in some implementations of simplified communication devices,such as voice recognition modules. Voice recognition modules can be usedfor instance to accept voice commands in connection with the user of thesimplified mobile communication device's 205 use in telephone call(e.g., to accept a vocal input of a particular telephone number orcontact name associated with a telephone number stored at simplifiedmobile communication device 205, prompting the dialing of thecorresponding telephone number). Voice recognition can also be used toprovide two-factor authentication, for instance, beginning withauthentication of a user at the simplified mobile communication device205 itself (e.g., based on a voice match), before allowing thesimplified mobile communication device 205 to be used as a physicaltoken to authenticate the same user to one or more cooperating computingdevices.

Cooperating computing devices (e.g., 210) can include robust computingfunctionality, including I/O and graphic display capabilities notavailable on simplified mobile communication devices 205. For instance,an example cooperating computing device 210, such as a tablet computer,smart phone, personal digital assistant, laptop or personal computer,can include one or more processors 245, memory elements 248, a graphicaldisplay 250, and a tactile user interface 254 capable of acceptingtactile inputs from a user, such as a keypad, touchscreen, trackball,touchpad, keyboard, mouse, or other such device or module. In additionto providing graphic display and I/O capabilities above that of thesimplified communication device 205, cooperating computing devices(e.g., 210) can also include more diversified and extensive software anddata storage capabilities. For instance, cooperating computing devices(e.g., 210) can include an operating system 252 and one or more softwareapplications 268, as well as data used by the software applications 268.In some examples, user profiles 270 can be maintained and stored (e.g.,in data store 265) on a cooperating computing device 210 to includeapplication data, and other files and data corresponding to a particularuser. A user of a particular simplified communication device (e.g., 205)can authenticate to the cooperating computing device 210 and/or aparticular user profile 270 so as to gain access to the data included inthe user profile. In other instances, all or a portion of the userprofile data can alternatively be stored on a simplified communicationdevice 205. In still other instances, all or a portion of user profiledata can be stored on devices remote from simplified communicationdevice 205 and cooperating computing devices (e.g., 210), includingcloud-based devices, the user profile data accessible to either or bothof the simplified communication device 205 and cooperating computingdevices (e.g., 210).

Cooperating computing devices 210 can include additional modules andfunctionality including a short range network adapter 255, I/O manager260, and device manager 262. A short range network adapter 255 can beadapted to facilitate a cooperating computing device's 210 participationin a communication session over one or more short range networks 135,such as Bluetooth or WiFi networks. I/O manager 260 can be used tocoordinate interaction with a cooperating simplified mobilecommunication device 205 over the short range network connection. Forinstance, user inputs received on the cooperating computing device'suser interfaces 254 can be communicated to a simplified mobilecommunication device 205 connected to the cooperating computing device210 over short range network 135. For example, a phone number can beselected or input by a user on a keypad of a cooperating computingdevice 210, prompting the phone number data to be forwarded tosimplified mobile communication device 205 and used by the simplifiedmobile communication device 205 to initiate a telephone call to thephone number received over the short range network 135 from thecooperating computing device 210. Additionally, data, such as a websiteor GUI of an application can be received from the simplified mobilecommunication device 205, such as data from one or more data or webservers (e.g., 165) over a wireless broadband connection, and renderedand displayed (e.g., using graphical display 250) on the cooperatingcomputing device.

As noted above, simplified mobile communication devices 205 can connectto and establish relationships with multiple different cooperatingcomputing devices. Similarly, a single cooperating computing device 210,such as a single tablet computer or personal computer, etc. can provideI/O support for and/or be authenticated to using multiple differentsimplified mobile communication devices 205. For instance, a singlecomputing device may maintain multiple different user profiles 270 andbe shared among multiple users, each with their own associatedsimplified mobile communication device 205. Accordingly, device manager262 can be used to manage relationships with pre-identified simplifiedmobile communication devices 205, for instance, to streamline connectionto and provide enhanced support for particular simplified mobilecommunication devices 205 with which a particular cooperating computingdevice 210 has already communicated. In some instances, the establishingof a relationship between a simplified mobile communication device 205and a cooperating computing device 210 can serve as a prerequisite toauthentication of a user at the cooperating computing device through thesharing of a GUUID 238, authentication data 240, and other data from thesimplified mobile communication device 205.

In one particular example, the GUUID 238 of the simplified mobilecommunication device can be private to the device 205 and not sharedwith or exposed to other devices. In some instances, a simplified mobilecommunication device 205 and a particular cooperating computing devicecan mutually authenticate, or pair, to the other. During such a pairing,certificates can be generated from the respective keys (e.g., the GUUID238 of the simplified mobile communication device 205), and combinedwith the public key of the other device for use in pairing andestablishing a trusted relationship between the two cooperating deviceswithout requiring the GUUID (or other keys) to be explicitly sharedbetween the devices.

Further, additional functionality can be provided through examplecooperating computing devices (e.g., 210). For example, in someinstances, cooperating computing devices 210, themselves, can includefunctionality for connecting to and communicating over various othercommunication networks, including the Internet 160 and even cellularnetworks 140. Further, certain cooperating computing device 210implementations can include other functionality including a cloud datamanager, for use in authenticating to and accessing data and services incloud computing environments (e.g., on behalf of a user authenticated tothe data using authentication data 240 provided through a cooperatingsimplified mobile communication device 205), contact lists and contactmanagement (e.g., including telephone numbers for speed-dialingparticular contacts), as well as voice recognition functionality andother functionality. While it is anticipated that in someimplementations of simplified mobile communication device 205, voiceand/or speech recognition capabilities will be resident on thesimplified mobile communication device 205 itself, in other examples,voice and/or speech recognition functionality can instead oradditionally be provided, at least in part, by a cooperating computingdevice 210. For example, a user can input voice data using themicrophone of simplified mobile communication device 205 and the voicedata can be communicated to a cooperating computing device (e.g., overshort range network 135) for voice and/or speech recognition processing.

Turning to FIG. 3A, example interactions and operations are representedin block diagram 300 a involving a simplified mobile communicationdevice, embodied in this particular example within an example hands-freeheadset telephone device 305, and cooperating computing device, such asan example touchscreen computer 310. Headset telephone 305 andtouchscreen computing device 310 can discover that the other device iswithin range of a particular short range wireless network 135 andestablish a connection, link, or pairing between the two devices 305,310, for instance, using traditional Bluetooth connection protocols.With a pairing established between headset telephone 305 and touchscreencomputing device 310, inputs can be received from a user interactingwith and providing inputs using a touchscreen interface 315 of computingdevice 310. In this particular example, a numeric keypad GUI ispresented on the touchscreen 315 and a user can input numberscorresponding to a particular telephone number. The telephone number canbe communicated to the headset telephone 305 and then used by theheadset telephone in the establishing of a telephone communicationsession over a cellular network 140. For instance, the headset telephonecan communicate the telephone number to a cellular base station 145 inconnection with the initiation of a telephone call with another deviceor network endpoint associated with the dialed telephone number enteredusing touchscreen 310.

FIG. 3B illustrates another example of interaction and operationsbetween devices 305, 310. In some instances, a telephone number can beselected by a user of touchscreen computing device 310 via an interfaceother than a numerical keypad interface, such as shown in FIG. 3A. Forinstance, some cooperating computing devices can include functionalityfor browsing and viewing web pages, and other files such as text, PDF,HTML, Adobe Flash, Java, and other files and scripts, including filesaccessed over a network (e.g., the Internet or private LAN) as well asfiles stored locally on the device 310. In some instances, an examplecooperating computing device (e.g., 310) can view a file that includesan identified telephone number, name of a contact, or other identifierthat can be used to identify a telephone number to be called usingsimplified mobile communication device (e.g., 305). As an example, inFIG. 3B, interactive content is displayed in graphical touchscreeninterface 315, such as a webpage of a business that includes contactinformation for the business. In some instances, telephone numbersincluded in the displayed file can be automatically identified orotherwise designated as being telephone numbers and presented on theuser interface as a selectable hyperlink (e.g., 325). In this particularexample, touchscreen computer 310 pairs to headset telephone 305 andreceives a user input, for instance, via the touchscreen interface 315selecting the telephone number hyperlink 325. Data communicating theselected telephone number can then be communicated to the headsettelephone 305 over a short range wireless network 135. As in the exampleof FIG. 3A, headset telephone 305 can receive the communicated telephonenumber and initiate and participate in a telephone call with devicesassociated with the communicated telephone number using cellular network140 and cellular base station 320.

In some examples, the content displayed on cooperating computing device310 can be received over a network, for instance, via a cellularbroadband data network (e.g., 140) using headset telephone device 305.Indeed, in some instances, headset telephone 305 can transmit datacollected from a remote web server or other source to the cooperatingcomputing device 310 for display on the cooperating computing device310. Other data and content can be accessed by the headset telephone 305and forwarded to the cooperating computing device 310 for display on theinterface 315 of the cooperating computing device, including globalpositioning system (GPS) data, SMS texts, audio, video, and other mediaincluding web pages, such as in the example of FIG. 3B. Further, in someinstances, at least a portion of the processing of the data passedthrough the headset telephone 305 from cellular data network 140 to thecooperating computing device 310, can be processed and prepared forrendering using the headset telephone 305. Thus, cooperating computingdevices (e.g., 310) can be developed that are substantially simpler infunctionality than current, expensive smartphone and tablet computingdevices, given that, in some implementations, much of the processing andnetwork access functionality can be provided through headset telephone305.

Modern conventional smart phones and personal computing devices, withtheir ever-expanding feature sets have also become expensive tomanufacture and purchase. Further, with the increased mobility ofcomputing devices, comes the enhanced risk of the devices being lost,stolen, forgotten, or damaged. Emerging security issues include the riskof unauthorized users accessing sensitive data, for instance, fromemails, digital photos, documents, SMS messages, voicemails, and otherfiles and data stored on portable computing devices. In some instances,simplified mobile communication devices (e.g., 305) can additionallyinclude mechanisms for authenticating a user of the simplified mobilecommunication device (e.g., 305) to one or more cooperating computingdevices (e.g., 310).

Given the simplified functionality of a simplified mobile communicationdevice, some implementations of simplified mobile communication devicecan be embodied in devices that are also quite small relative to othercellular communication devices. By providing a device without a tactileinterface or large display, a simplified mobile communication build canbe slight enough to make the device easily wearable by a user. Forinstance, in the example of FIG. 4A, simplified mobile communicationdevice 305 can be embodied as a headset telephone that can be wornaround the ear of a user. Other implementations can also be wearable,such as simplified cellular telephone devices that can be worn as anecklace, as a lapel clip or brooch, a watch, or other implementationscapable of being used as a telephone while being conveniently worn by auser. While conventional cellular phones are often carried in purses,pockets, and clipped to belts, conventional devices are often removedfrom their carriers, such as during dialing, viewing of graphicaldisplays, and phone calls, providing opportunities for the cell phone tobe separated from its user. In some instances, a wearable simplifiedcellular telephone device cannot only be worn, but can be continue to beworn while the user makes a phone call. Indeed, providing for a wearablesimplified mobile communication device can create a more reliable andconsistent link between a device and a user. Consequently, in someinstances, simplified mobile communication device can function as aphysical token to authenticate the user of the simplified mobilecommunication devices to cooperating computing devices used incooperation with the simplified mobile communication device.

In the example of FIG. 4A, a user 405 carrying or wearing simplifiedheadset telephone 305 carried or worn by a particular user 405 canconnect to a cooperating computing device 310 capable, among otherthings, of providing I/O support to the simplified headset telephone 305(e.g., via a touchpad interface 315). Prior to granting the user accessto the cooperating touchpad device 310, authentication data, stored orsourced by the headset telephone device 305, can be sent andcommunicated to the cooperating computing device 310 and used by thecooperating computing device to authenticate a user associated with theauthentication data sent by the headset telephone device 305 to thecooperating computing device 305.

In instances where a user trusts the security of a simplified mobilecommunication device, for instance, because the user wears or isotherwise in nearly constant possession of the simplified mobilecommunication device (e.g., given, it's size and ease of carrying), theuser can elect to have the simplified mobile communication device serveas a wireless and convenient mechanism for authenticating the user tothe user's devices, including devices the user is likely to use as acooperating device in connection with the simplified mobilecommunication device 305. This can also simplify a user's use ofmultiple cooperating devices, allowing a user to, in some cases, to movefrom one device to another and automatically authenticate to the devicesas the user 405 (i.e., the carried the simplified mobile communicationdevice 305) comes within range of the device (e.g., defined by a rangeof a short range wireless network or other radio-frequency-basedtechnique).

In some instances, one or more cooperating computing devices (e.g., 310)can be locked and rendered inoperable pending authentication by aparticular simplified mobile communication device 305. While in someinstances, authentication data exchanged with a cooperating computingdevice by mobile communication device 305 unlocks certain user profiledata (i.e., data authorized for access by a particular user), in otherinstances, a particular cooperating computing device itself can beunlocked through a successful authentication of the mobile communicationdevice 305 to the particular cooperating computing device 310. In suchinstances, a cooperating computing device's 310 operation can bedependent on a particular simplified mobile communication device 305being collocated with the cooperating computing device 310, theparticular simplified mobile communication device 305 serving as awireless key to secure one or more of a user's computing devices (e.g.,tablets, laptops, gaming systems, hard drives, etc.) from unauthorizedaccess.

A variety of authentication types and authentication data can be used inconnection with a simplified communication device authenticating itsuser to a cooperating computing device (e.g., 310), including examplesdiscussed above. In one illustrative example, a simplified mobilecommunication device 305 can authenticate to a cooperating computingdevice 310 using a certificate exchange between the devices 305, 310.For instance, the simplified mobile communication device 305, uponidentifying a potential cooperating computing device, can request accessto the cooperating computing device 310. The simplified mobilecommunication device 305 can pass a certificate to the cooperatingcomputing device 310. In some instances, the passing of the certificatecan be in connection with an initial pairing of the devices 305, 310.The cooperating computing device 310 can verify the received certificateand generate a key, for instance, for use in subsequent communicationswith the devices 305, 310. The simplified mobile communication device305 can similarly utilize a certificate received from the cooperatingcomputing device 310 and generate its own key for use in communicationswith the cooperating computing device 310. Generation of such keys byeither device can be based on and generated from both an internal key,device ID, GUUID, or other data internal to the device as well as data(e.g., a certificate) received from the other device in the pairing.Further, simplified mobile communication device 305 and cooperatingcomputing device 310 can communicate securely, for instance, utilizingauthenticated network access protocols such as EAP, EAP-TLS, EAP-MS-CHAPv2, and PEAP or other standard. Additionally, wireless protectionprotocols such as WEP, WPA, WPA2, etc. can also be used, among othertechniques to secure communications between simplified mobilecommunication devices (e.g., 305) and cooperating computing devices(e.g., 310).

In some instances, two-factor security or authentication measures can beapplied in connection with a simplified mobile communication device(e.g., 305) authenticating to a cooperating computing device (e.g.,310). In some instances, prior to using a particular simplified mobilecommunication device (e.g., 305) to authenticate a user to a cooperatingcomputing device (e.g., 310), the particular simplified device andparticular cooperating device can negotiate a relationship governingtheir cooperative functioning and communications. For instance, anencryption scheme can be pre-negotiated between a simplified device andcooperating device to ensure that data communicated between the devicesover a short-range wireless network (e.g., 135) are secure. In suchinstances, the authentication data sent from the simplified device canitself be encrypted as it is communicated from the simplified device tothe cooperating device. The cooperating device can utilize theauthentication data to authenticate the user of the simplified device tothe cooperating device.

Two-factor (or, more generally, multi-factor) security or authenticationschemes can be used to generally provide additional security against anunauthorized user gaining access to a simplified mobile communicationdevice and thereby also associated cooperating computing devices. Forinstance, in the example of FIG. 4B, a two-factor authentication schemeis illustrated where a user provides a PIN number, password, or otheruser-entered passkey or data, supplementing the authentication datastored at and communicated from the simplified device 305 to thecooperating device 310. For example, a user 405 can interact with aninterface (e.g., 315) of the cooperating touchscreen device 310 tosupply a password, PIN, or other data indicating that the user 405 isauthorized, not only to use the cooperating computing device 310, butalso the simplified headset telephone 305. For example, were headsettelephone 305 to fall into the hands of an unauthorized user, theunauthorized user could easily also gain access to cooperating computingdevices recognizing and authenticating users by virtue of a connectionwith and receiving authentication data from the headset telephone 305.

Given the limited functionality of some implementations of simplifiedcommunication devices (e.g., 305), restricting a user's access tocompatible or pre-identified and -configured cooperating devices (e.g.,devices with which a corresponding simplified communication device hasestablished a relationship) can effectively also protect againstunauthorized use of the simplified communication device. In yet anotherexample, illustrated in FIG. 4C, a two-factor authentication scheme canbe implemented using authentication data communicated to a cooperatingcomputing device (e.g., 310) by a simplified communication device (e.g.,305) using inputs received at the simplified communication device. Inone example, a user 405 of the simplified communication device, asimplified headset telephone 305 in the example of FIG. 4C, can receivevoice inputs from the user 405 in connection with an authentication ofthe user. For example, in some implementations, headset telephone 305can include voice recognition functionality adapted to process voicedata received through a microphone of the headset telephone 305 anddetermine whether the voice data substantially matches a voice sample ofone or more authorized users of the headset telephone 305. In otherimplementations, it can be advantageous to provide the voice recognitionfunctionality on the more functionally robust cooperating devices usedin connection with the simplified mobile communication devices. Forinstance, in one example, a relationship can be established between aparticular simplified communication device and one or more cooperatingcomputing devices by pre-negotiating a voice-recognition step in theauthentication of a user to the simplified communication device and/orcooperating computing device. Pre-negotiating a voice-recognition stepcan include the recording, sharing, and maintaining of voice sample dataof authorized users of the cooperating computing devices. For example,voice sample data can be captured using the microphone of headsettelephone 305 and communicated to a cooperating computing device (e.g.,310) in connection with setting-up a voice recognition check. Subsequentto the negotiation of a voice recognition check, a user can enter voicedata using the microphone of the headset telephone 305 and the voicedata can be sent to cooperating computing device for voice-recognitionprocessing to check if the current user's voice matches a stored voicesample of an authorized user. Depending on the outcome of the voiceanalysis, a user (e.g., 405) can be granted or denied access to eitheror both of the cooperating computing device and simplified communicationdevice. In other instances, voice recognition processing can be providedon the simplified headset telephone 305 and the outcome of the voicerecognition can be the basis for determining whether to allow theheadset telephone 305 to connect to other devices. Indeed, in someinstances, if a voice recognition check fails, the simplified mobilecommunication device 305 can be disabled, temporarily or permanently.

As illustrated in FIG. 5, simplified mobile communication devices (e.g.,505) can operate cooperatively with multiple different cooperatingdevices (e.g., 515, 520). Similarly, a single cooperating device (e.g.,515) can operate cooperatively with multiple simplified mobilecommunication devices (e.g., 505, 510). For instance, a user of a singlemobile communication device (e.g., 505) can utilize a plurality ofdifferent devices to accept inputs or display outputs on behalf of thesimplified device 505. For example, a user can carry or wear asimplified mobile communication device 505, 510 throughout the day andmay come in contact with or be in closest proximity to multipledifferent devices that can serve effectively as I/O peripherals of thesimplified mobile communication device 505. For example, a user candesire to place a telephone call while seated in front of a personalcomputer (e.g., 515) in one instance, and use the personal computer totype or otherwise enter a telephone number that can be communicated to(e.g., over a short range wireless network connection or session) andused by the simplified mobile communication device 505 to place thephone call. In a subsequent instance, the user may wish to place asecond telephone call while using or in proximity of another, differentcooperating computing device. For example, the user can access a devicesuch as a notepad computer, portable media player, in-car navigation ormedia controller device, video game console, computer kiosk or otherpublic computer, or another computing device adapted to accept userinputs via a tactile user interface (such as a controller, keypad,mouse, touchpad, video game controller, or other tactile inputmechanism) and input the telephone number of the second phone call usingthe second cooperating computing device. The entered telephone numbercan then be communicated to and used by the simplified mobilecommunication device over a short-range wireless communication session.Allowing a mobile communication device to accept inputs from, send datafor graphical rendering to, or otherwise operate cooperatively withmultiple different cooperating computing devices can permit a user toenjoy the benefits of, in some cases, a smaller, lighter, and moreconvenient simplified mobile communication device untethered to a singleI/O device that can add girth and awkwardness to the design of a mobilecommunication device.

In some instances, a particular user can have access to multiplecellular network access accounts, such as one for their personalcellular voice communications, one for their business cellular voicecommunications, one for their personal mobile broadband data usage, onefor their business broadband data usage, among many other examples. Intraditional cases, users are forced to carry multiple cellphones,wireless broadband cards, mobile hotspot devices, etc. for each of theirmultiple accounts. In some implementations, a simplified mobilecommunication device can include or have access to SIM data for each ofthe plurality of accounts. In some instances, a user can designate whichof the accounts the user wishes to use for a particular communication,such as a cellular phone call, using the simplified mobile communicationdevice by using, authorizing to, or receiving input from a particularcooperating computing device. For example, a particular cooperatingcomputing device can be configured to correspond to a particularaccount. Accordingly, by using or authenticating to a particularcooperating computing device, a particular account can also beidentified, and in some cases, SIM or other data transmitted between thecooperating computing device and the simplified mobile communicationdevice allowing the simplified mobile communication device to establishcellular communication sessions under the identified account. In otherexamples, a user can use an interface of a cooperating computing deviceto select one of a plurality of accounts for use in a particularcellular communication using the simplified mobile communication device,among other examples.

As noted above, an example cooperating computing device (e.g., 515) canalso serve as an I/O device and maintain relationships with multipledifferent simplified mobile communication devices (e.g., 505, 510). Forexample, in a household where multiple simplified communication devicesare owned and utilized (and associated with particular users), one ormore computing devices can be used as cooperating computing devicesshared between the multiple simplified communication devices. Public,semi-public, or other shared computing devices can also be configured toconnect to and provide I/O support to multiple simplified mobilecommunication devices associated with a plurality of different users,such as in an internet café, university computer lab, officeenvironment, or other environment. In still other examples, kioskcomputing devices can be provided that are configured with touchpads, orother user interface devices, together with short range networkingcapabilities (e.g., using Bluetooth, WiFi, or another protocol),allowing the kiosk devices to connect to and serve as a publiccooperating computing device for use by numerous simplified mobilecommunication devices and their users. In some implementations, asimplified mobile communication device can pair to the kiosk, forinstance using a once-only pairing (e.g., that does not result incredentials of the simplified mobile communication device being storedby the kiosk). In some respects, such public or semi-public kiosks couldserve as a substitute for (or be provided in connection with) publictelephone booths or other public communications or computing services oroutposts. Such a kiosk can establish communication sessions with aparticular one of a plurality of detected simplified mobilecommunication devices and allow a corresponding user to access thedevice to place a telephone call or access data (e.g., over a cellularbroadband data network) for presentation on the kiosk using thesimplified mobile communication device. In other instances, use of akiosk can be tracked and monetized, so that users of the kiosk arebilled according to their use of the kiosk.

In some implementations, a simplified mobile communication device canserve as an authentication token, providing authentication datacorresponding to the user of the simplified mobile communication. Insome instances, by connecting to a simplified mobile communicationdevice and receiving authentication data from the simplified mobilecommunication device (and, in some cases, receiving additionalcorroborating authentication data, such as a PIN, password, or voicesignature) a particular cooperating computing device can identify aparticular user (i.e., of the simplified mobile communication device)and access profiles and other data (including files, application data,contact lists, email, histories, and other data associated with orauthorized for access by the particular user) (collectively “userprofile data” (e.g., 525 a, 525 b, 530)) corresponding to theauthenticated user. For example, particular user profile data (e.g., 525a, 525 b, 530) can be accessed using particular cooperating computingdevices (e.g., 515, 520). In some instances, particular user data (e.g.,325 b) corresponding to one or more users can be stored locally inmemory (e.g., 535) of a cooperating computing device and made availableupon authentication of the corresponding user. For example, a first userof a simplified mobile communication device (e.g., a headset cellulartelephone 505) can utilize the simplified mobile communication device505 to authenticate the first user on a cooperating computing device 520to access particular user profile data 525 b stored on the device 520.In some instances, user profile data 525 b stored on the cooperatingdevice 520 can be used in connection with the functionality of thesimplified mobile communication device. For instance, user profile data525 b can include a user's contacts including telephone numbersassociated with the contacts. In some instances, user profile data 525 bcan include data tied to a particular network service provider (e.g., toidentify that calls placed while using the cooperating computing deviceare to be attributed to a particular network service contract associatedwith the particular cooperating computing device 510, such as SIM data,among other examples).

In some instances, authentication of a user to a particular cooperatingcomputing device can serve to allow access to user profile data (e.g.,525 a, 530) stored remotely from the cooperating computing device andmobile communication device (e.g., 505, 510). For instance, user profiledata 525 a, 530 for a plurality of users can be maintained in adistributed computing environment, such as server pools or cloud-baseddata storage environments (e.g., 540). In some examples, a cloud sessioncan be established through and linked to a simplified mobilecommunication device. The cloud session can allow data to persistbetween various cooperating devices authenticated to using thesimplified mobile communication device. For instance, a user can begintyping an email or other document on a first cooperating computingdevice and move to a second cooperating computing device, maintainingthe cloud session and allowing the user to access and continue draftingthe incomplete email from the first cooperating computing device. Acooperating computing device (e.g., 515) can serve as a client to thedata servers (e.g., 545) and utilize authentication data provided by asimplified mobile communication device (e.g., 505, 510) to gainauthorization to access and/or be provisioned with data maintained bythe cloud-based data store 545 for a user associated with the simplifiedmobile communication device. Alternatively, authentication data tocloud-based data store 545 can be maintained at the cooperatingcomputing device 515, with the authentication data of the simplifiedcommunication device 505 serving to unlock use of the cooperatingcomputing device 515 and thereby also the data in data store 540 or thecooperating computing device's access to remote data stores (e.g., 545).

In some examples, multiple, different user profiles 525 a, 530, eachassociated with a different user (via an associated simplified mobilecommunication device (e.g., 505, 510)) can be accessed using a singlecooperating computing device (e.g., 515). For example, cooperatingcomputing device 515 can establish a connection with one of a pluralityof simplified mobile communication devices 505, 510 and authenticate auser to the cooperating computing device 515 based on authenticationdata received from the respective simplified mobile communicationdevice. Through the authentication data (and/or user identificationdata) received from the respective simplified mobile communicationdevice, the cooperating computing device 515 can identify user profiledata for the corresponding user, including files and data with accessrestricted to the corresponding user. Such profile data can be includedamong a plurality of profiles, and stored locally on the cooperatingcomputing device. In other instances, the user profile data can beaccessible from a remote storage system (e.g., 540) and theauthentication data received from the simplified mobile communicationdevice can be used to authenticate the cooperating computing device'access to the remote data store.

In still further examples, the use of remote or cloud-based user profiledata stores can allow a user to provision one of a plurality ofdifferent devices with user profile data. In one implementation,simplified mobile communication devices (e.g., 505, 510) can provideauthentication data to one of a plurality of cooperating computingdevices allowing the cooperating computing device to retrieve userprofile data from a remote data store (e.g., 545) and provision thecooperating computing device with the user profile data. In someinstances, provisioning the cooperating computing device can serve to atleast temporarily cause the cooperating computing device to mirror thepersonal setting and data present on the user's personal computer(s).Accordingly, through the use of simplified mobile communication device,a user can move from one computing device to the next and allow theirpersonal data to be provided (at least temporarily) on each of thedevices. In some instances, the cooperating computing devices merelyserve as a client for accessing and changing data that is stored andmaintained at the remote data store 545. In either event, a user caneasily make use of multiple computing devices while enjoying access totheir personal data and files, all while enjoying the security providedby linking access to the personal user profiles to the user's possessionof (and in some cases authorization to) a simplified mobilecommunication device associated with the user.

Further, in addition to at least partially unlocking data, applications,and functionality of a cooperating computing device through the sharingof authentication data by virtue of collocation of a particularsimplified mobile communication device with the cooperating computingdevice, a particular simplified mobile communication device can also beused to authenticate a user to the peripherals of a cooperatingcomputing device. For instance, a particular cooperating computingdevice, such as a laptop, may be connected, wirelessly or by wireline,to detachable hard drive devices, printers, disk readers, credit cardreaders, web cameras, monitors, and other peripheral hardware. In someinstances, use of particular peripherals (such as a particulardetachable hard drive, or space within that hard drive) can be disabledpending authentication of a user to the cooperating computing deviceusing the particular simplified mobile communication device. In suchinstances, a simplified mobile communication device can serve as a keyfor unlocking multiple cooperating computing devices through a singleauthentication.

FIGS. 6A-6B are simplified flowcharts 600 a-b illustrating exampletechniques for cooperatively using a simplified communication devicewith a cooperating computing device. In a first example, illustrated inflowchart 600 a, a cooperating computing device can be detected 605 by asimplified communication device, such as a headset telephone lacking auser interface capable of receiving telephone numbers via tactile inputsor other similar space-intensive user interfaces. The cooperatingcomputing device can be detected 605 as being substantially collocatedwith the simplified communication device, such as residing within rangeof a common short range wireless network, such as a Bluetooth piconet. Acommunication session can be established 610 between the simplifiedcommunication device and the cooperating computing device, for instance,over the short-range wireless network. Establishing 610 thecommunication session can include handshaking and the exchange of otherdata used to coordinate communication between the devices throughout thesession, such as according to traditional Bluetooth communicationprotocols. In some instances, establishing 610 the communication sessioncan include establishing a relationship between the devices orrecognizing a pre-existing relationship between the devices. Suchrelationships can be associated with particular users or user accounts.Within the established communication session, user inputs can bereceived through one or more user interfaces of the cooperatingcomputing device and passed to the simplified mobile communicationdevice for use by the simplified communication device in connection withcommunications over a cellular network. For instance, the input data caninclude a telephone number. The simplified communication device canestablish 620 a telephone call over the cellular network using thetelephone number entered at the cooperating computing device. Otherinformation can be communicated by the simplified mobile communicationdevice over a cellular network using or based on data received from acooperating computing device, including requests for data, such as webpages and other electronic media served by host devices on the Internet.

In the flowchart 600 b of FIG. 6B, example operations of a cooperatingcomputing device are illustrated, including the detection 625 of asimplified mobile communication device substantially collocated with thecomputing device and seeking to use I/O functions of the computingdevice. For example, a simplified mobile communication device can beidentified as present in or within range of a short-range wirelessnetwork. A communication session can be established 630 with thesimplified mobile communication device and authentication data can bereceived 635 from the simplified mobile communication device. Aparticular user (e.g., the user of the simplified mobile communicationdevice) can be authenticated 640 based on the received authenticationdata. Authentication data can include a digital certificate orsignature, encryption key, token, voice sample, or other authenticationdata. Supplemental authentication data can also be received from a user,such as a PIN, password, voice sample, etc. to verify that the user isrightfully in possession of the simplified mobile communication devicebeing used as a physical token to authenticate a user to the cooperatingcomputing device. Upon authentication, user inputs can be received 645through one or more user interfaces of the cooperating computing device,such as a keyboard, touchscreen, mouse, trackball, joystick, video gamecontroller, keypad, or other user interface capable of receiving tactileinputs from a user. The received inputs can then be sent 650 to thesimplified mobile communication device, for instance, over the shortrange wireless network. The simplified mobile communication device canthen use the inputs from the cooperating computing device to establishconnections and exchange data over one or more cellular networks.

Although this disclosure has been described in terms of certainimplementations and generally associated methods, alterations andpermutations of these implementations and methods will be apparent tothose skilled in the art. For example, the actions described herein canbe performed in a different order than as described and still achievethe desirable results. As one example, the processes depicted in theaccompanying figures do not necessarily require the particular ordershown, or sequential order, to achieve the desired results. Systems andtools illustrated can similarly adopt alternate architectures,components, and modules to achieve similar results and functionality.For instance, in certain implementations, multitasking, parallelprocessing, and cloud-based solutions may be advantageous. In onealternative system or tool, the wireless authentication functionality ofa simplified mobile communication device can be employed on a removablestorage device, such as a portable hard drive, thumb drive, or the like.In such instances, the removable storage device can lack a userinterface but possess wireless access functionality for connecting tocooperating computing devices over a short-range network, such asBluetooth, and sharing authentication data with the cooperatingcomputing devices over the short-range network to authenticate theholder of the wireless, portable storage device to one or morecooperating computing devices, allowing the user to both gain access to(and secure) the cooperating computing device through the wirelessstorage device as well as access, consume, and modify data stored on thehard drive using the authenticated-to cooperating computing device.Other systems and tools can also make use of principles of thisdisclosure. Additionally, diverse user interface layouts andfunctionality can be supported. Other variations are within the scope ofthe following claims.

Embodiments of the subject matter and the operations described in thisspecification can be implemented in digital electronic circuitry, or incomputer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them. Embodiments of the subject matterdescribed in this specification can be implemented as one or morecomputer programs, i.e., one or more modules of computer programinstructions, encoded on computer storage medium for execution by, or tocontrol the operation of, data processing apparatus. Alternatively or inaddition, the program instructions can be encoded on an artificiallygenerated propagated signal, e.g., a machine-generated electrical,optical, or electromagnetic signal that is generated to encodeinformation for transmission to suitable receiver apparatus forexecution by a data processing apparatus. A computer storage medium canbe, or be included in, a computer-readable storage device, acomputer-readable storage substrate, a random or serial access memoryarray or device, or a combination of one or more of them. Moreover,while a computer storage medium is not a propagated signal per se, acomputer storage medium can be a source or destination of computerprogram instructions encoded in an artificially generated propagatedsignal. The computer storage medium can also be, or be included in, oneor more separate physical components or media (e.g., multiple CDs,disks, or other storage devices), including a distributed softwareenvironment or cloud computing environment.

Networks, including core and access networks, including wireless accessnetworks, can include one or more network elements. Network elements canencompass various types of routers, switches, gateways, bridges,loadbalancers, firewalls, servers, inline service nodes, proxies,processors, modules, or any other suitable device, component, element,or object operable to exchange information in a network environment. Anetwork element may include appropriate processors, memory elements,hardware and/or software to support (or otherwise execute) theactivities associated with using a processor for screen managementfunctionalities, as outlined herein. Moreover, the network element mayinclude any suitable components, modules, interfaces, or objects thatfacilitate the operations thereof. This may be inclusive of appropriatealgorithms and communication protocols that allow for the effectiveexchange of data or information.

The operations described in this specification can be implemented asoperations performed by a data processing apparatus on data stored onone or more computer-readable storage devices or received from othersources. The terms “data processing apparatus,” “processor,” “processingdevice,” and “computing device” can encompass all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing. The apparatus can includegeneral or special purpose logic circuitry, e.g., a central processingunit (CPU), a blade, an application specific integrated circuit (ASIC),or a field-programmable gate array (FPGA), among other suitable options.While some processors and computing devices have been described and/orillustrated as a single processor, multiple processors may be usedaccording to the particular needs of the associated server. Referencesto a single processor are meant to include multiple processors whereapplicable. Generally, the processor executes instructions andmanipulates data to perform certain operations. An apparatus can alsoinclude, in addition to hardware, code that creates an executionenvironment for the computer program in question, e.g., code thatconstitutes processor firmware, a protocol stack, a database managementsystem, an operating system, a cross-platform runtime environment, avirtual machine, or a combination of one or more of them. The apparatusand execution environment can realize various different computing modelinfrastructures, such as web services, distributed computing and gridcomputing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, module, (software) tools, (software) engines, orcode) can be written in any form of programming language, includingcompiled or interpreted languages, declarative or procedural languages,and it can be deployed in any form, including as a standalone program oras a module, component, subroutine, object, or other unit suitable foruse in a computing environment. For instance, a computer program mayinclude computer-readable instructions, firmware, wired or programmedhardware, or any combination thereof on a tangible medium operable whenexecuted to perform at least the processes and operations describedherein. A computer program may, but need not, correspond to a file in afile system. A program can be stored in a portion of a file that holdsother programs or data (e.g., one or more scripts stored in a markuplanguage document), in a single file dedicated to the program inquestion, or in multiple coordinated files (e.g., files that store oneor more modules, sub programs, or portions of code). A computer programcan be deployed to be executed on one computer or on multiple computersthat are located at one site or distributed across multiple sites andinterconnected by a communication network.

Programs can be implemented as individual modules that implement thevarious features and functionality through various objects, methods, orother processes, or may instead include a number of sub-modules, thirdparty services, components, libraries, and such, as appropriate.Conversely, the features and functionality of various components can becombined into single components as appropriate. In certain cases,programs and software systems may be implemented as a composite hostedapplication. For example, portions of the composite application may beimplemented as Enterprise Java Beans (EJBs) or design-time componentsmay have the ability to generate run-time implementations into differentplatforms, such as J2EE (Java 2 Platform, Enterprise Edition), ABAP(Advanced Business Application Programming) objects, or Microsoft's.NET, among others. Additionally, applications may represent web-basedapplications accessed and executed via a network (e.g., through theInternet). Further, one or more processes associated with a particularhosted application or service may be stored, referenced, or executedremotely. For example, a portion of a particular hosted application orservice may be a web service associated with the application that isremotely called, while another portion of the hosted application may bean interface object or agent bundled for processing at a remote client.Moreover, any or all of the hosted applications and software service maybe a child or sub-module of another software module or enterpriseapplication (not illustrated) without departing from the scope of thisdisclosure. Still further, portions of a hosted application can beexecuted by a user working directly at a server hosting the application,as well as remotely at a client.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform actions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), tablet computer, a mobile audio or videoplayer, a game console, a Global Positioning System (GPS) receiver, or aportable storage device (e.g., a universal serial bus (USB) flashdrive), to name just a few. Devices suitable for storing computerprogram instructions and data include all forms of non-volatile memory,media and memory devices, including by way of example semiconductormemory devices, e.g., EPROM, EEPROM, and flash memory devices; magneticdisks, e.g., internal hard disks or removable disks; magneto opticaldisks; and CD ROM and DVD-ROM disks. The processor and the memory can besupplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a CRT (cathode ray tube) or LCD (liquidcrystal display) monitor, for displaying information to the user and akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device, includingremote devices, which are used by the user.

Embodiments of the subject matter described in this specification can beimplemented in a computing system that includes a back end component,e.g., as a data server, or that includes a middleware component, e.g.,an application server, or that includes a front end component, e.g., aclient computer having a graphical user interface or a Web browserthrough which a user can interact with an implementation of the subjectmatter described in this specification, or any combination of one ormore such back end, middleware, or front end components. The componentsof the system can be interconnected by any form or medium of digitaldata communication, e.g., a communication network. Examples ofcommunication networks include any internal or external network,networks, sub-network, or combination thereof operable to facilitatecommunications between various computing components in a system. Anetwork may communicate, for example, Internet Protocol (IP) packets,Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice,video, data, and other suitable information between network addresses.The network may also include one or more local area networks (LANs),radio access networks (RANs), metropolitan area networks (MANs), widearea networks (WANs), all or a portion of the Internet, peer-to-peernetworks (e.g., ad hoc peer-to-peer networks), and/or any othercommunication system or systems at one or more locations.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits data (e.g., an HTML page) to a clientdevice (e.g., for purposes of displaying data to and receiving userinput from a user interacting with the client device). Data generated atthe client device (e.g., a result of the user interaction) can bereceived from the client device at the server.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of particular inventions.Certain features that are described in this specification in the contextof separate embodiments can also be implemented in combination in asingle embodiment. Conversely, various features that are described inthe context of a single embodiment can also be implemented in multipleembodiments separately or in any suitable subcombination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims. In somecases, the actions recited in the claims can be performed in a differentorder and still achieve desirable results. In addition, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults.

What is claimed is:
 1. A method comprising: detecting a firstcommunication device as substantially collocated with a wireless headsetdevice using a short-range wireless network; establishing a connectionbetween the first communication device and the wireless headset deviceover the short-range wireless network; receiving input data from thefirst communication device over the short-range wireless networkspecifying a telephone number for a telephone call using the wirelessheadset device; establishing a connection between the wireless headsetdevice and a cellular base station to initiate the telephone call with asecond communication device associated with the telephone number.
 2. Themethod of claim 1, wherein the wireless headset device is adapted tocapture voice inputs and output audio.
 3. The method of claim 1, furthercomprising: receiving voice inputs at the wireless headset device; andsending voice data corresponding to the received voice inputs to thecellular base station in connection with the telephone call.
 4. Themethod of claim 3, wherein the voice data is sent by the wirelessheadset device.
 5. The method of claim 3, further comprising: receivingcommunications from the second communication device forwarded by acellular base station in connection with the telephone call; andpresenting audio outputs at the wireless headset device corresponding tothe received communications.
 6. The method of claim 1, furthercomprising: sending authentication data from the wireless headset deviceto the first communication device, wherein the authentication data isused by the first communication device to authenticate a user to thefirst communication device.
 7. The method of claim 6, wherein theauthentication data includes an encryption key and content accessiblethrough the first communication device is decrypted based at least inpart on the received encryption key.
 8. The method of claim 6, whereinthe authentication data is sent over the short-range wireless network.9. The method of claim 6, wherein the authentication data includes atleast one of a digital certificate, digital signature, and an encryptionkey.
 10. The method of claim 6, wherein authentication of the user tothe first communication device includes receiving second authenticationdata from the user at the first communication device.
 11. The method ofclaim 10, wherein the second authentication data includes a personalidentification number (PIN) entered by the user at an interface of thefirst communication device.
 12. The method of claim 6, wherein use ofthe first communication device is locked pending authentication to thefirst communication device using the wireless headset device.
 13. Themethod of claim 1, further comprising: detecting a third communicationdevice as substantially collocated with the wireless headset deviceusing a short-range wireless network; establishing a connection betweenthe third communication device and the wireless headset device over ashort-range wireless network; receiving second input data from the thirdcommunication device over a short-range wireless network specifying atelephone number for a second telephone call using the wireless headsetdevice; and establishing a connection between the wireless headsetdevice and a cellular base station to initiate the second telephonecall.
 14. The method of claim 1, wherein the short-range wirelessnetwork is at least one of a Bluetooth piconet and a WiFi local areanetwork.
 15. The method of claim 1, further comprising: receiving voiceinput from a user; comparing the voice input to a voice profile for theuser; and authenticating the user on the wireless headset device basedon the comparison.
 16. An apparatus comprising: a processor device; amemory element including user authentication data and user identifierdata; a short-range wireless network adapter; and device coordinatoradapted to: detect a first communication device as substantiallycollocated with the apparatus using a short-range wireless network;establish a connection with the first communication device over theshort-range wireless network; and communicate the user authenticationdata to the first communication device over the short-range wirelessnetwork to authenticate a particular user to the first communicationdevice.
 17. The apparatus of claim 16, wherein the device coordinator isfurther adapted to receive input data from the first communicationdevice over the short-range wireless network specifying a telephonenumber for a telephone call and the apparatus further comprises: amicrophone; a speaker; a cellular adapter including an antenna andadapted to: establish a connection with a cellular base station toinitiate the telephone call with a second communication deviceassociated with the telephone number.
 18. The apparatus of claim 17,further comprising a voice recognition module adapted to authenticate auser based on voice inputs received at the microphone.
 19. The apparatusof claim 16, wherein the apparatus lacks a tactile input interface. 20.The apparatus of claim 15, wherein the apparatus lacks a graphical userdisplay.
 21. A method comprising: detecting a first communication deviceas substantially collocated with a second communication device using ashort-range wireless network; establishing a connection between thefirst communication device and the second communication device over theshort-range wireless network; receiving authentication data from thefirst communication device over the short-range wireless network; usingthe authentication data to authenticate a particular user to the secondcommunication device; and sending a telephone number to the firstcommunication device for use by the first communication device inestablishing a telephone call with another device associated with thetelephone number.
 22. The method of claim 20, further comprising:receiving a user-entered authentication input in addition to theauthentication data, wherein both the received authentication data anduser-entered authentication input are used to authenticate theparticular user to the second communication device.
 23. The method ofclaim 21, wherein the user-entered authentication input is a voicesample for comparison with a voice recognition sample for the particularuser.
 24. The method of claim 21, wherein the user-enteredauthentication input is a passkey.
 25. The method of claim 20, furthercomprising: identifying user profile data corresponding to theparticular user based on the received authentication data; providingaccess to the user profile data through a user interface of the secondcommunication device.
 26. The method of claim 25, wherein the userprofile data is identified from a set of profile data associated with aplurality of user profiles including a user profile of the particularuser.
 27. The method of claim 25, wherein the user profile data ishosted by a storage device remote from the second communication deviceand providing access to the user profile data includes authenticatingaccess to the storage device.
 28. Logic encoded in non-transitory mediathat includes code for execution and when executed by a processor isoperable to perform operations comprising: detecting a firstcommunication device as substantially collocated with a secondcommunication device using a short-range wireless network; establishinga connection between the first communication device and the secondcommunication device over the short-range wireless network; receivingauthentication data from the first communication device over theshort-range wireless network; using the authentication data toauthenticate a particular user to the second communication device; andsending a telephone number to the first communication device for use bythe first communication device in establishing a telephone call withanother device associated with the telephone number.